Power control with flexible scheduling delay

ABSTRACT

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive a transmit power control (TPC) command in a grant associated with transmitting an uplink communication. A scheduling delay between the grant and the uplink communication may be a flexible scheduling delay. The UE may sample a TPC state in association with determining a transmit power, and may determine the transmit power based at least in part on the TPC state and the TPC command. In some aspects, a UE may detect a power headroom report (PHR) trigger associated with a carrier of a plurality of carriers. The UE may identify a set of carriers that is to be ignored when calculating a power headroom, and may calculate the power headroom based at least in part on ignoring the identified set of carriers. Numerous other aspects are provided.

CROSS REFERENCE TO RELATED APPLICATION UNDER 35 U.S.C § 119

This application claims priority to U.S. Provisional Application No.62/670,564, filed on May 11, 2018, entitled “TECHNIQUES AND APPARATUSESFOR POWER CONTROL WITH FLEXIBLE SCHEDULING DELAY,” which is herebyexpressly incorporated by reference herein.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wirelesscommunication, and more particularly to techniques and apparatuses forpower control with flexible scheduling delay.

BACKGROUND

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (e.g., bandwidth,transmit power, etc.). Examples of such multiple-access technologiesinclude code division multiple access (CDMA) systems, time divisionmultiple access (TDMA) systems, frequency-division multiple access(FDMA) systems, orthogonal frequency-division multiple access (OFDMA)systems, single-carrier frequency-division multiple access (SC-FDMA)systems, time division synchronous code division multiple access(TD-SCDMA) systems, and Long Term Evolution (LTE). LTE/LTE-Advanced is aset of enhancements to the Universal Mobile Telecommunications System(UMTS) mobile standard promulgated by the Third Generation PartnershipProject (3GPP).

A wireless communication network may include a number of base stations(BSs) that can support communication for a number of user equipment(UEs). A user equipment (UE) may communicate with a base station (BS)via the downlink and uplink. The downlink (or forward link) refers tothe communication link from the BS to the UE, and the uplink (or reverselink) refers to the communication link from the UE to the BS. As will bedescribed in more detail herein, a BS may be referred to as a Node B, agNB, an access point (AP), a radio head, a transmit receive point (TRP),a New Radio (NR) BS, a 5G Node B, and/or the like.

The above multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent user equipment to communicate on a municipal, national,regional, and even global level. New Radio (NR), which may also bereferred to as 5G, is a set of enhancements to the LTE mobile standardpromulgated by the Third Generation Partnership Project (3GPP). NR isdesigned to better support mobile broadband Internet access by improvingspectral efficiency, lowering costs, improving services, making use ofnew spectrum, and better integrating with other open standards usingorthogonal frequency division multiplexing (OFDM) with a cyclic prefix(CP) (CP-OFDM) on the downlink (DL), using CP-OFDM and/or SC-FDM (e.g.,also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) onthe uplink (UL), as well as supporting beamforming, multiple-inputmultiple-output (MIMO) antenna technology, and carrier aggregation.However, as the demand for mobile broadband access continues toincrease, there exists a need for further improvements in LTE and NRtechnologies. Preferably, these improvements should be applicable toother multiple access technologies and the telecommunication standardsthat employ these technologies.

SUMMARY

In some aspects, a method for wireless communication, performed by auser equipment, may include receiving a transmit power control (TPC)command in a grant associated with transmitting an uplink communication,wherein a scheduling delay between the grant and the uplinkcommunication is a flexible scheduling delay; sampling a TPC state inassociation with determining a transmit power for transmitting theuplink communication; and determining the transmit power based at leastin part on the TPC state and the TPC command.

In some aspects, a user equipment for wireless communication may includememory and one or more processors configured to receive a TPC command ina grant associated with transmitting an uplink communication, wherein ascheduling delay between the grant and the uplink communication is aflexible scheduling delay; sample a TPC state in association withdetermining a transmit power for transmitting the uplink communication;and determine the transmit power based at least in part on the TPC stateand the TPC command.

In some aspects, a non-transitory computer-readable medium may store oneor more instructions for wireless communication. The one or moreinstructions, when executed by one or more processors of a userequipment, may cause the one or more processors to receive a TPC commandin a grant associated with transmitting an uplink communication, whereina scheduling delay between the grant and the uplink communication is aflexible scheduling delay; sample a TPC state in association withdetermining a transmit power for transmitting the uplink communication;and determine the transmit power based at least in part on the TPC stateand the TPC command.

In some aspects, an apparatus for wireless communication may includemeans for receiving a TPC command in a grant associated withtransmitting an uplink communication, wherein a scheduling delay betweenthe grant and the uplink communication is a flexible scheduling delay;means for sampling a TPC state in association with determining atransmit power for transmitting the uplink communication; and means fordetermining the transmit power based at least in part on the TPC stateand the TPC command.

In some aspects, a method for wireless communication, performed by auser equipment, may include detecting a power headroom report (PHR)trigger, wherein the user equipment is configured to transmit uplinkcommunications using a plurality of carriers; identifying, based atleast in part on detecting the PHR trigger, a set of carriers, of theplurality of carriers, that is to be ignored when calculating a powerheadroom associated with a carrier of the plurality of carriers; andcalculating the power headroom based at least in part on an uplinktransmission, associated with the carrier, and based at least in part onignoring the set of carriers that is to be ignored.

In some aspects, a user equipment for wireless communication may includememory and one or more processors configured to detect a PHR trigger,wherein the user equipment is configured to transmit uplinkcommunications using a plurality of carriers; identify, based at leastin part on detecting the PHR trigger, a set of carriers, of theplurality of carriers, that is to be ignored when calculating a powerheadroom associated with a carrier of the plurality of carriers; andcalculate the power headroom based at least in part on an uplinktransmission, associated with the carrier, and based at least in part onignoring the set of carriers that is to be ignored.

In some aspects, a non-transitory computer-readable medium may store oneor more instructions for wireless communication. The one or moreinstructions, when executed by one or more processors of a userequipment, may cause the one or more processors to detect a PHR trigger,wherein the user equipment is configured to transmit uplinkcommunications using a plurality of carriers; identify, based at leastin part on detecting the PHR trigger, a set of carriers, of theplurality of carriers, that is to be ignored when calculating a powerheadroom associated with a carrier of the plurality of carriers; andcalculate the power headroom based at least in part on an uplinktransmission, associated with the carrier, and based at least in part onignoring the set of carriers that is to be ignored.

In some aspects, an apparatus for wireless communication may includemeans for detecting a PHR trigger, wherein the apparatus is configuredto transmit uplink communications using a plurality of carriers; meansfor identifying, based at least in part on detecting the PHR trigger, aset of carriers, of the plurality of carriers, that is to be ignoredwhen calculating a power headroom associated with a carrier of theplurality of carriers; and means for calculating the power headroombased at least in part on an uplink transmission, associated with thecarrier, and based at least in part on ignoring the set of carriers thatis to be ignored.

Aspects generally include a method, apparatus, system, computer programproduct, non-transitory computer-readable medium, user equipment, basestation, wireless communication device, and processing system assubstantially described herein with reference to and as illustrated bythe accompanying drawings and specification.

The foregoing has outlined rather broadly the features and technicaladvantages of examples according to the disclosure in order that thedetailed description that follows may be better understood. Additionalfeatures and advantages will be described hereinafter. The conceptionand specific examples disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present disclosure. Such equivalent constructions do notdepart from the scope of the appended claims. Characteristics of theconcepts disclosed herein, both their organization and method ofoperation, together with associated advantages will be better understoodfrom the following description when considered in connection with theaccompanying figures. Each of the figures is provided for the purposesof illustration and description, and not as a definition of the limitsof the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can beunderstood in detail, a more particular description, briefly summarizedabove, may be had by reference to aspects, some of which are illustratedin the appended drawings. It is to be noted, however, that the appendeddrawings illustrate only certain typical aspects of this disclosure andare therefore not to be considered limiting of its scope, for thedescription may admit to other equally effective aspects. The samereference numbers in different drawings may identify the same or similarelements.

FIG. 1 is a block diagram conceptually illustrating an example of awireless communication network, in accordance with various aspects ofthe present disclosure.

FIG. 2 is a block diagram conceptually illustrating an example of a basestation in communication with a user equipment (UE) in a wirelesscommunication network, in accordance with various aspects of the presentdisclosure.

FIGS. 3A and 3B are diagrams illustrating examples associated withtransmit power control with flexible scheduling delay, in accordancewith various aspects of the present disclosure.

FIG. 4 is a diagram illustrating an example process performed, forexample, by a user equipment, in accordance with various aspects of thepresent disclosure.

FIG. 5 is a diagram illustrating an example of power headroomcalculation with flexible scheduling delay, in accordance with variousaspects of the present disclosure.

FIG. 6 is a diagram illustrating an example process performed, forexample, by a user equipment, in accordance with various aspects of thepresent disclosure.

DETAILED DESCRIPTION

In some wireless networks, such as a NR network, an amount of time(i.e., a scheduling delay) between a grant, and an uplink communicationassociated with the grant, is flexible (i.e., can vary dynamically witheach grant/uplink communication). This differs from other types ofnetworks, such as a Long-Term Evolution (LTE) network, where suchscheduling delays are not flexible (i.e., are fixed or are functions ofonly semi-static configurations rather than of any dynamic informationin grants).

As an example, in a NR network, a scheduling delay between a first grant(received in a physical downlink control channel (PDCCH)) and a firstphysical uplink shared channel (PUSCH) communication scheduled by thefirst grant, may differ from a scheduling delay between a second grantand a second PUSCH communication scheduled by the second grant. ThisPDCCH-to-PUSCH scheduling delay may be identified by a k2 parameteridentified in a given grant.

As another example, a scheduling delay between a first grant, associatedwith a first physical downlink shared channel (PDSCH) communication, andan acknowledgment or negative acknowledgment feedback (ACK/NACK)associated with the first PDSCH communication , may differ from ascheduling delay between a second grant, associated with a second PDSCHcommunication, and an ACK/NACK associated with the second PDSCHcommunication. In this example, the variation may result fromflexibility in a scheduling delay between grants and PDSCHcommunications and/or from flexibility in a scheduling delay betweenPDSCH communications and ACKs/NACKs. The PDCCH-to-PDSCH scheduling delaymay be identified by a k0 parameter, while the PDSCH-to-ACK/NACKscheduling delay may be identified by a k1parameter, either or both ofwhich may be identified in a given grant. A UE capability may support aminimum value for these parameters, so that the UE has enough time toprocess the grant and the PDSCH (in case of downlink grants) which maybe identified by n0, n1, and n2 parameters respectively. Further, theseparameters may have units of slots or of OFDM symbols. For example, k0,k1, and k2 may be in units of slots, while n0, n1, and n2 may be inunits of symbols.

A transmit power control (TPC) command may also be included in a grant.The TPC command may indicate an amount by which to increment a transmitpower in association with transmitting an uplink communication (e.g., aPUSCH communication scheduled by an uplink grant, an ACK/NACK associatedwith a PDSCH communication scheduled by a downlink grant, and/or thelike). In other words, the TPC command may be used to implementclosed-loop power control. In some cases, multiple TPC processes can beconfigured. For example, the UE may be configured with separate TPCprocesses for physical uplink control channel (PUCCH) power control andPUSCH power control. Further, each TPC process may use one or more powercontrol loops. In such cases, each TPC command may be associated with aparticular TPC process and a particular power control loop associatedwith the TPC process.

However, due to the flexible nature of scheduling delay, a manner inwhich a UE processes a given TPC command may be ambiguous. For example,the UE receives a first uplink grant at time to that schedules a firstuplink communication (e.g., a PUSCH communication) at time t3, andreceives a second uplink grant at time t1 (e.g., a time after time toand before time t3) that schedules a second uplink communication at timet2 (e.g., a time before time t3). In this example, the UE may not beconfigured with information that indicates how the UE should process afirst TPC command and a second TPC command, included in the first uplinkgrant and the second uplink grant, respectively (e.g., whether/how thefirst TPC command should be applied to the transmission of the seconduplink communication, whether/how the second TPC command should beapplied to the transmission of the first uplink communication, and/orthe like).

Some aspects described herein provide techniques and apparatuses forpower control with flexible scheduling delay. In some aspects, a UE mayreceive a TPC command in a grant associated with transmitting an uplinkcommunication, wherein a scheduling delay between the grant and theuplink communication is a flexible scheduling delay. Here, the UE maysample a TPC state in association with determining a transmit power fortransmitting the uplink communication, and may determine the transmitpower based at least in part on the TPC state and the TPC command. Insome aspects, the UE may accumulate the TPC command into the TPC (e.g.,before sampling the TPC state or after sampling the TPC state).Additional details regarding a manner in which the UE samples the TPCstate and (optionally) accumulates the TPC command into the TPC stateare described below.

The use of flexible scheduling delay also presents issues regardingcalculation of power headrooms by the UE in carrier aggregation (CA)scenarios (e.g., when the UE is configured to transmit uplinkcommunications using multiple carriers). Due to flexible scheduling,concurrent or overlapping transmissions of uplink communications (ondifferent carriers) may be transmitted after scheduling delays ofdifferent length (e.g., since the associated grants may be received atdifferent times). Generally, the UE is configured to report a powerheadroom for every active (e.g., scheduled) carrier upon detecting apower headroom report (PHR) trigger. For a carrier on which a grant wasreceived before an earliest grant received after the PHR trigger wasdetected, the UE may be configured to report an actual power headroom.Conversely, for a carrier on which a grant was received after the firstgrant received after the PHR trigger was detected, the UE may beconfigured to report a reference power headroom (e.g., an estimatedpower headroom, sometimes referred to as virtual power headroom, forwhich a maximum power reduction (MPR) and/or an additional MPR (A-MPR)are set to 0 during calculation).

Here, for carriers on which grants come before the earliest grant afterthe PHR trigger, uplink communications scheduled by later arrivinggrants are unknown. However, the power headrooms associated with thesecarriers need to be calculated for inclusion in a PHR transmitted in theuplink. Due to time constraints, the UE cannot wait until all othergrants are received before beginning the power headroom calculation(e.g., the UE must begin calculation of the power headrooms forinclusion in an uplink communication scheduled by the earliest grantafter the PHR trigger). Thus, one or more parameters associated withcalculating power headroom for a given carrier that depend on actualtransmissions of uplink communications on all carriers (e.g., a MPR, aA-MPR, a power management MPR (P-MPR), and/or the like) would need to becalculated without knowledge of uplink transmission associated withlater arriving grants.

Further, in the case of mixed numerology across carriers, an uplinkcommunication transmitted on a carrier with a comparatively lowersubcarrier spacing (SCS) may overlap with two or more uplinkcommunications transmitted on a carrier with a comparatively higher SCS.Here, the UE may not have knowledge regarding a manner in which toselect a particular uplink communication on the carrier with the higherSCS that is to be considered in a power headroom calculation for theuplink communication on the carrier with the lower SCS. Further, the UEmay not have knowledge regarding a manner in which the UE should selecta particular uplink communication on the carrier with the higher SCSthat is to be reported in a PHR.

Some aspects described herein provide techniques and apparatuses forpower headroom calculation in a CA scenario with flexible scheduling. Insome aspects, the UE may detect a PHR trigger associated with a carrierof a plurality of carriers, identify a set of carriers, of a pluralityof carriers, that is to be ignored when calculating a power headroomassociated with the carrier, and calculate the power headroom based atleast in part on an uplink transmission, associated with the carrier,and based at least in part on ignoring the set of carriers that is to beignored. Additional details regarding a manner in which the UEcalculates power headroom in a CA scenario with flexible scheduling aredescribed below.

Various aspects of the disclosure are described more fully hereinafterwith reference to the accompanying drawings. This disclosure may,however, be embodied in many different forms and should not be construedas limited to any specific structure or function presented throughoutthis disclosure. Rather, these aspects are provided so that thisdisclosure will be thorough and complete, and will fully convey thescope of the disclosure to those skilled in the art. Based on theteachings herein one skilled in the art should appreciate that the scopeof the disclosure is intended to cover any aspect of the disclosuredisclosed herein, whether implemented independently of or combined withany other aspect of the disclosure. For example, an apparatus may beimplemented or a method may be practiced using any number of the aspectsset forth herein. In addition, the scope of the disclosure is intendedto cover such an apparatus or method which is practiced using otherstructure, functionality, or structure and functionality in addition toor other than the various aspects of the disclosure set forth herein. Itshould be understood that any aspect of the disclosure disclosed hereinmay be embodied by one or more elements of a claim.

Several aspects of telecommunication systems will now be presented withreference to various apparatuses and techniques. These apparatuses andtechniques will be described in the following detailed description andillustrated in the accompanying drawings by various blocks, modules,components, circuits, steps, processes, algorithms, etc. (collectivelyreferred to as “elements”). These elements may be implemented usinghardware, software, or combinations thereof. Whether such elements areimplemented as hardware or software depends upon the particularapplication and design constraints imposed on the overall system.

It should be noted that while aspects may be described herein usingterminology commonly associated with 3G and/or 4G wireless technologies,aspects of the present disclosure can be applied in othergeneration-based communication systems, such as 5G and later, includingNR technologies.

FIG. 1 is a diagram illustrating a network 100 in which aspects of thepresent disclosure may be practiced. The network 100 may be an LTEnetwork or some other wireless network, such as a 5G or NR network.Wireless network 100 may include a number of BSs 110 (shown as BS 110 a,BS 110 b, BS 110 c, and BS 110 d) and other network entities. A BS is anentity that communicates with user equipment (UEs) and may also bereferred to as a base station, a NR BS, a Node B, a gNB, a 5G node B(NB), an access point, a transmit receive point (TRP), and/or the like.Each BS may provide communication coverage for a particular geographicarea. In 3GPP, the term “cell” can refer to a coverage area of a BSand/or a BS subsystem serving this coverage area, depending on thecontext in which the term is used.

A BS may provide communication coverage for a macro cell, a pico cell, afemto cell, and/or another type of cell. A macro cell may cover arelatively large geographic area (e.g., several kilometers in radius)and may allow unrestricted access by UEs with service subscription. Apico cell may cover a relatively small geographic area and may allowunrestricted access by UEs with service subscription. A femto cell maycover a relatively small geographic area (e.g., a home) and may allowrestricted access by UEs having association with the femto cell (e.g.,UEs in a closed subscriber group (CSG)). ABS for a macro cell may bereferred to as a macro BS. ABS for a pico cell may be referred to as apico BS. A BS for a femto cell may be referred to as a femto BS or ahome BS. In the example shown in FIG. 1, a BS 110 a may be a macro BSfor a macro cell 102 a, a BS 110 b may be a pico BS for a pico cell 102b, and a BS 110 c may be a femto BS for a femto cell 102 c. ABS maysupport one or multiple (e.g., three) cells. The terms “eNB”, “basestation”, “NR BS”, “gNB”, “TRP”, “AP”, “node B”, “5G NB”, and “cell” maybe used interchangeably herein.

In some examples, a cell may not necessarily be stationary, and thegeographic area of the cell may move according to the location of amobile BS. In some examples, the BSs may be interconnected to oneanother and/or to one or more other BSs or network nodes (not shown) inthe access network 100 through various types of backhaul interfaces suchas a direct physical connection, a virtual network, and/or the likeusing any suitable transport network.

Wireless network 100 may also include relay stations. A relay station isan entity that can receive a transmission of data from an upstreamstation (e.g., a BS or a UE) and send a transmission of the data to adownstream station (e.g., a UE or a BS). A relay station may also be aUE that can relay transmissions for other UEs. In the example shown inFIG. 1, a relay station 110 d may communicate with macro BS 110 a and aUE 120 d in order to facilitate communication between BS 110 a and UE120 d. A relay station may also be referred to as a relay BS, a relaybase station, a relay, etc.

Wireless network 100 may be a heterogeneous network that includes BSs ofdifferent types, e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.These different types of BSs may have different transmit power levels,different coverage areas, and different impacts on interference inwireless network 100. For example, macro BSs may have a high transmitpower level (e.g., 5 to 40 Watts) whereas pico BSs, femto BSs, and relayBSs may have lower transmit power levels (e.g., 0.1 to 2 Watts).

A network controller 130 may couple to a set of BSs and may providecoordination and control for these BSs. Network controller 130 maycommunicate with the BSs via a backhaul. The BSs may also communicatewith one another, e.g., directly or indirectly via a wireless orwireline backhaul.

UEs 120 (e.g., 120 a, 120 b, 120 c) may be dispersed throughout wirelessnetwork 100, and each UE may be stationary or mobile. A UE may also bereferred to as an access terminal, a terminal, a mobile station, asubscriber unit, a station, etc. A UE may be a cellular phone (e.g., asmart phone), a personal digital assistant (PDA), a wireless modem, awireless communication device, a handheld device, a laptop computer, acordless phone, a wireless local loop (WLL) station, a tablet, a camera,a gaming device, a netbook, a smartbook, an ultrabook, a medical deviceor equipment, biometric sensors/devices, wearable devices (smartwatches, smart clothing, smart glasses, smart wrist bands, smart jewelry(e.g., smart ring, smart bracelet)), an entertainment device (e.g., amusic or video device, or a satellite radio), a vehicular component orsensor, smart meters/sensors, industrial manufacturing equipment, aglobal positioning system device, or any other suitable device that isconfigured to communicate via a wireless or wired medium.

Some UEs may be considered machine-type communication (MTC) or evolvedor enhanced machine-type communication (eMTC) UEs. MTC and eMTC UEsinclude, for example, robots, drones, remote devices, sensors, meters,monitors, location tags, etc., that may communicate with a base station,another device (e.g., remote device), or some other entity. A wirelessnode may provide, for example, connectivity for or to a network (e.g., awide area network such as Internet or a cellular network) via a wired orwireless communication link. Some UEs may be consideredInternet-of-Things (IoT) devices, and/or may be implemented as NB-IoT(narrowband internet of things) devices. Some UEs may be considered aCustomer Premises Equipment (CPE). UE 120 may be included inside ahousing that houses components of UE 120, such as processor components,memory components, and/or the like.

In general, any number of wireless networks may be deployed in a givengeographic area. Each wireless network may support a particular RAT andmay operate on one or more frequencies. A RAT may also be referred to asa radio technology, an air interface, etc. A frequency may also bereferred to as a carrier, a frequency channel, etc. Each frequency maysupport a single RAT in a given geographic area in order to avoidinterference between wireless networks of different RATs. In some cases,NR or 5G RAT networks may be deployed.

In some examples, access to the air interface may be scheduled, whereina scheduling entity (e.g., a base station) allocates resources forcommunication among some or all devices and equipment within thescheduling entity's service area or cell. Within the present disclosure,as discussed further below, the scheduling entity may be responsible forscheduling, assigning, reconfiguring, and releasing resources for one ormore subordinate entities. That is, for scheduled communication,subordinate entities utilize resources allocated by the schedulingentity.

Base stations are not the only entities that may function as ascheduling entity. That is, in some examples, a UE may function as ascheduling entity, scheduling resources for one or more subordinateentities (e.g., one or more other UEs). In this example, the UE isfunctioning as a scheduling entity, and other UEs utilize resourcesscheduled by the UE for wireless communication. A UE may function as ascheduling entity in a peer-to-peer (P2P) network, and/or in a meshnetwork. In a mesh network example, UEs may optionally communicatedirectly with one another in addition to communicating with thescheduling entity. In some aspects, a scheduling delay associated withan uplink communication (e.g., a communication to be transmitted by UE120 to BS 110) may be a flexible scheduling delay, and UE 120 may beperform transmit power control and/or power headroom calculation asdescribed elsewhere herein.

Thus, in a wireless communication network with a scheduled access totime—frequency resources and having a cellular configuration, a P2Pconfiguration, and a mesh configuration, a scheduling entity and one ormore subordinate entities may communicate utilizing the scheduledresources.

In some aspects, two or more UEs 120 (e.g., shown as UE 120 a and UE 120e) may communicate directly using one or more sidelink channels (e.g.,without using a base station 110 as an intermediary to communicate withone another). For example, the UEs 120 may communicate usingpeer-to-peer (P2P) communications, device-to-device (D2D)communications, a vehicle-to-everything (V2X) protocol (e.g., which mayinclude a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure(V2I) protocol, and/or the like), a mesh network, and/or the like. Inthis case, the UE 120 may perform scheduling operations, resourceselection operations, and/or other operations described elsewhere hereinas being performed by the base station 110.

As indicated above, FIG. 1 is provided merely as an example. Otherexamples may differ from what is described with regard to FIG. 1.

FIG. 2 shows a block diagram of a design 200 of base station 110 and UE120, which may be one of the base stations and one of the UEs in FIG. 1.Base station 110 may be equipped with T antennas 234 a through 234 t,and UE 120 may be equipped with R antennas 252 a through 252 r, where ingeneral T≥1 and R≥1.

At base station 110, a transmit processor 220 may receive data from adata source 212 for one or more UEs, select one or more modulation andcoding schemes (MCS) for each UE based at least in part on channelquality indicators (CQIs) received from the UE, process (e.g., encodeand modulate) the data for each UE based at least in part on the MCS(s)selected for the UE, and provide data symbols for all UEs. Transmitprocessor 220 may also process system information (e.g., for semi-staticresource partitioning information (SRPI), etc.) and control information(e.g., CQI requests, grants, upper layer signaling, etc.) and provideoverhead symbols and control symbols. Transmit processor 220 may alsogenerate reference symbols for reference signals (e.g., thecell-specific reference signal (CRS)) and synchronization signals (e.g.,the primary synchronization signal (PSS) and secondary synchronizationsignal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO)processor 230 may perform spatial processing (e.g., precoding) on thedata symbols, the control symbols, the overhead symbols, and/or thereference symbols, if applicable, and may provide T output symbolstreams to T modulators (MODs) 232 a through 232 t. Each modulator 232may process a respective output symbol stream (e.g., for OFDM, etc.) toobtain an output sample stream. Each modulator 232 may further process(e.g., convert to analog, amplify, filter, and upconvert) the outputsample stream to obtain a downlink signal. T downlink signals frommodulators 232 a through 232 t may be transmitted via T antennas 234 athrough 234 t, respectively. According to various aspects described inmore detail below, the synchronization signals can be generated withlocation encoding to convey additional information.

At UE 120, antennas 252 a through 252 r may receive the downlink signalsfrom base station 110 and/or other base stations and may providereceived signals to demodulators (DEMODs) 254 a through 254 r,respectively. Each demodulator 254 may condition (e.g., filter, amplify,downconvert, and digitize) a received signal to obtain input samples.Each demodulator 254 may further process the input samples (e.g., forOFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtainreceived symbols from all R demodulators 254 a through 254 r, performMIMO detection on the received symbols if applicable, and providedetected symbols. A receive processor 258 may process (e.g., demodulateand decode) the detected symbols, provide decoded data for UE 120 to adata sink 260, and provide decoded control information and systeminformation to a controller/processor 280. A channel processor maydetermine reference signal received power (RSRP), received signalstrength indicator (RSSI), reference signal received quality (RSRQ),channel quality indicator (CQI), etc.

On the uplink, at UE 120, a transmit processor 264 may receive andprocess data from a data source 262 and control information (e.g., forreports comprising RSRP, RSSI, RSRQ, CQI, etc.) fromcontroller/processor 280. Transmit processor 264 may also generatereference symbols for one or more reference signals. The symbols fromtransmit processor 264 may be precoded by a TX MIMO processor 266 ifapplicable, further processed by modulators 254 a through 254 r (e.g.,for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to base station 110. Atbase station 110, the uplink signals from UE 120 and other UEs may bereceived by antennas 234, processed by demodulators 232, detected by aMIMO detector 236 if applicable, and further processed by a receiveprocessor 238 to obtain decoded data and control information sent by UE120. Receive processor 238 may provide the decoded data to a data sink239 and the decoded control information to controller/processor 240.Base station 110 may include communication unit 244 and communicate tonetwork controller 130 via communication unit 244. Network controller130 may include communication unit 294, controller/processor 290, andmemory 292.

In some aspects, one or more components of UE 120 may be included in ahousing. Controller/processor 240 of base station 110,controller/processor 280 of UE 120, and/or any other component(s) ofFIG. 2 may perform one or more techniques associated with power controlwith flexible scheduling delay and/or power headroom determination withflexible scheduling delay, as described in more detail elsewhere herein.For example, controller/processor 240 of base station 110,controller/processor 280 of UE 120, and/or any other component(s) ofFIG. 2 may perform or direct operations of, for example, process 400 ofFIG. 4, process 600 of FIG. 6, and/or other processes as describedherein. Memories 242 and 282 may store data and program codes for basestation 110 and UE 120, respectively. A scheduler 246 may schedule UEsfor data transmission on the downlink and/or uplink.

In some aspects, UE 120 may include means for receiving a TPC command ina grant associated with transmitting an uplink communication, wherein ascheduling delay between the grant and the uplink communication is aflexible scheduling delay; means for sampling a TPC state in associationwith determining a transmit power for transmitting the uplinkcommunication; means for determining the transmit power based at leastin part on the TPC state and the TPC command; and/or the like. In someaspects, such means may include one or more components of UE 120described in connection with FIG. 2.

In some aspects, UE 120 may include means for detecting a PHR trigger,wherein UE 120 is configured to transmit uplink communications using aplurality of carriers; means for identifying, based at least in part ondetecting the PHR trigger, a set of carriers, of the plurality ofcarriers, that is to be ignored when calculating a power headroomassociated with a carrier of the plurality of carriers; means forcalculating the power headroom based at least in part on an uplinktransmission, associated with the carrier, and based at least in part onignoring the set of carriers that is to be ignored; and/or the like. Insome aspects, such means may include one or more components of UE 120described in connection with FIG. 2.

While blocks in FIG. 2 are illustrated as distinct components, thefunctions described above with respect to the blocks may be implementedin a single hardware, software, or combination component or in variouscombinations of components. For example, the functions described withrespect to the transmit processor 264, the receive processor 258, and/orthe TX MIMO processor 266 may be performed by or under the control ofprocessor 280.

As indicated above, FIG. 2 is provided merely as an example. Otherexamples may differ from what is described with regard to FIG. 2.

FIGS. 3A and 3B are diagrams illustrating examples of transmit powercontrol with flexible scheduling delay, in accordance with variousaspects of the present disclosure.

As shown in FIG. 3A, and by reference number 305, a UE (e.g., UE 120)may receive a TPC command included in a grant associated with an uplinkcommunication. In some aspects, the uplink communication associated withthe grant may be a PUSCH communication, a physical uplink controlchannel (PUCCH) communication, an ACK/NACK, a sounding reference signal(SRS), a physical random access channel (PRACH) sequence, or anothertype of uplink communication. In some aspects, the grant may includeinformation that identifies a scheduling delay, as described above.

For example, the UE may receive an uplink grant associated withscheduling a PUSCH communication, where the grant includes informationthat identifies a k2 parameter that identifies a scheduling delaybetween the uplink grant and the PUSCH communication. As anotherexample, the UE may receive a downlink grant associated with schedulinga PUCCH communication (e.g., an ACK/NACK) for a PDSCH communicationscheduled by the downlink grant. Here, the grant may include informationthat identifies a k0 parameter that identifies a scheduling delaybetween the downlink grant and the PDSCH communication and/or a k1parameter that identifies a scheduling delay between the PDSCHcommunication and the PUCCH communication.

As shown by reference number 310, the UE may sample a TPC state inassociation with determining a transmit power for transmitting theuplink communication. The TPC state is a state variable that representsa transmit power level. In some aspects, the UE may determine a transmitpower for transmitting the uplink communication based at least in parton a result of sampling the TPC state, as described below. In someaspects, the UE may store the TPC state (e.g., in a register configuredon the UE). In some aspects, the UE may modify the TPC state based atleast in part on the TPC command, as described in further detail below.

As further indicated by reference number 310, the UE may sample the TPCstate at time T_(sample). In some aspects, time T_(sample) (i.e., thetime at which the UE samples the TPC state) may be relative to the grant(e.g., the UE may determine time T_(sample) relative to a time at whichthe UE received the grant). In some aspects, time T_(sample) may berelative to a resource associated with transmitting the uplinkcommunication (e.g., the UE may determine time T_(sample) relative to atime at which the uplink communication is scheduled).

In some aspects, an amount of time between the grant and T_(sample) oran amount of time between T_(sample) and the resource (depending onwhich T_(sample) is determined relative to) may be based at least inpart on the scheduling delay between the grant and the uplinkcommunication (e.g., such that a first scheduling delay causes the UE tosample the TPC state at a comparatively different time than a time atwhich a second scheduling delay causes the UE to sample the TPC state).Additionally, or alternatively, the amount of time may be based at leastin part on a grant type of the grant (e.g., such that a downlink grantcauses the UE to sample the TPC state at a comparatively different timethan a time at which an uplink grant causes the UE to sample the TPCstate). Additionally, or alternatively, the amount of time may be basedat least in part on a capability of the UE, for example, on one or moreof the capability parameters n0, n1, and n2.

In some aspects, the amount of time may be semistatically configured ormay be dynamically determined by the UE. In some aspects, informationthat identifies the amount of time may be signaled to the UE in downlinkcontrol information (DCI), may be a preconfigured constant, or may be afunction of one or more DCI parameters. In some aspects, the amount oftime may be on a symbol-level granularity, a slot-level granularity,and/or the like.

As further shown in FIG. 3A, and by reference number 315, the UE mayaccumulate the TPC command into the TPC state. In some aspects, the UEmay accumulate the TPC command into the TPC state by modifying (e.g.,adding, subtracting, or leaving unchanged) an amount of transmit power,identified by the TPC state, by an amount of transmit power identifiedby the TPC command. In some aspects, the UE may update the TPC statestored by the UE based at least in part on accumulating the TPC commandinto the TPC state. In some aspects, accumulating the TPC command intothe TPC state is optional (e.g., the UE may be configured not toaccumulate the TPC command into the TPC state).

As further indicated by reference number 315, the UE may accumulate theTPC command into the TPC state at time T_(add).. In some aspects, timeT_(add) (i.e., the time at which the UE accumulates the TPC command intothe TPC state) may be relative to the grant (e.g., the UE may determinetime T_(add) relative to a time at which the UE received the grant). Insome aspects, time T_(add) may be relative to a resource associated withtransmitting the uplink communication (e.g., the UE may determine timeT_(add) relative to a time at which the uplink communication isscheduled).

In some aspects, an amount of time between the grant and T_(add) or anamount of time between T_(add) and the resource (depending on whichT_(add) is determined relative to) may be based at least in part on thescheduling delay between the grant and the uplink communication (e.g.,such that a first scheduling delay causes the UE to add the TPC commandto the TPC state at a comparatively different time than a time at whicha second scheduling delay causes the UE to add the TPC command to theTPC state). Additionally, or alternatively, the amount of time may bebased at least in part on a grant type of the grant (e.g., such that adownlink grant causes the UE to add the TPC command to the TPC state ata comparatively different time than a time at which an uplink grantcauses the UE to add the TPC command to the TPC state). Additionally, oralternatively, the amount of time may be based at least in part on acapability of the UE (for example, on one or more of the capabilityparameters n0, n1, or n2).

In some aspects, the amount of time may be semistatically configured ormay be dynamically determined by the UE. In some aspects, informationthat identifies the amount of time may be signaled to the UE in DCI, maybe a preconfigured constant, or may be a function of one or more DCIparameters. In some aspects, the amount of time may be on a symbol-levelgranularity, a slot-level granularity, and/or the like.

In some aspects, the UE may be configured to accumulate the TPC commandinto the TPC state before the UE samples the TPC state. In some aspects,the UE may be configured to accumulate the TPC command into the TPCstate after the UE samples the TPC state. In some aspects, the UE may beconfigured to accumulate the TPC command into the TPC state and samplethe TPC state at a same time (e.g., such that the TPC command isaccumulated into the TPC state concurrently with the TPC state beingsampled).

In some aspects, when timing of the TPC state being sampled by the UEcoincides with timing of at least one TPC command being accumulated intothe TPC state, the UE may be configured to sample the TPC state afterthe at least one TPC command is accumulated into the TPC state (e.g.,such that a result of sampling the TPC state will reflect theaccumulation of the TPC command).

In some aspects, when timing of the TPC state being sampled by the UEcoincides with timing of at least one TPC command being accumulated intothe TPC state, the UE may be configured to sample the TPC state beforethe at least one TPC command is accumulated into the TPC state (e.g.,such that a result of sampling the TPC state will not reflect theaccumulation of the TPC command). In such a case, when the at least oneTPC command is the TPC command associated with the grant that caused theUE to sample the TPC state, the UE may be configured to add the TPCcommand to a result of sampling the TPC state.

As further shown by FIG. 3A, and by reference number 320, the UE maydetermine a transmit power based at least in part on a result ofsampling the TPC state. For example, the UE may determine that atransmit power, at which the UE is to transmit the uplink communication,is identified by the result of the TPC state (i.e., the result ofsampling the TPC state may identify the transmit power). As anotherexample, the UE may determine that the transmit power, at which the UEis to transmit the uplink communication, is identified by the result ofsampling the TPC state plus the TPC command (e.g., the result ofsampling the TPC state plus the TPC command may identify the transmitpower uplink). This may be the case when, for example, the UE samplesthe TPC state before accumulating the TPC command into the TPC state, orwhen the UE does not accumulate the TPC command into the TPC state.

As shown by reference number 325, the UE may transmit the uplinkcommunication at the transmit power determined as described above. Inthis way, a UE may be configured to manage power control for uplinkcommunications with flexible scheduling delay.

FIG. 3B illustrates various example aspects associated with powercontrol with flexible scheduling delay. For each example aspect, the UEhas received a first grant that includes a first TPC command (TPC1) andschedules a first uplink communication (UL1), and has received a secondgrant that includes a second TPC command (TPC2) and schedules a seconduplink communication (UL2). The uplink communications may be PUSCHtransmissions (e.g., when the grants are uplink grants) or PUCCHtransmissions carrying ACK/NACK (e.g., when the grants are downlinkgrants).

With reference to example 350 in FIG. 3B, the UE may be configured todetermine both T_(sample) and T_(add) relative to the respective grants(rather than the resources associated with the respective uplinkcommunications). As further shown, the UE may be configured such that anamount of time between the grant and T_(sample) matches an amount oftime between the grant and T_(add). As shown, in association with thefirst grant, the UE accumulates TPC1 into the TPC state and samples theTPC state at time T_(add1) (which matches time T_(sample1)). As furthershown, in association with the second grant, the UE accumulates TPC2into the TPC state and samples the TPC state at time T_(add2) (whichmatches time T_(sample2)). As a result, as shown, a transmit power forUL2 is based at least in part on TPC1 and TPC2 (e.g., since TPC1 andTPC2 were accumulated into the TPC state before or concurrently with thesampling of the TPC state at T_(sample2)). Here, as further shown, atransmit power for UL1 will be based at least in part on TPC1 but willnot be based on TPC2 (e.g., since TPC2 was not accumulated into the TPCstate until after the UE sampled the TPC state at T_(sample1)).

With reference to example 360 in FIG. 3B, the UE may be configured todetermine T_(add) relative to the respective grants and may beconfigured to determine T_(sample) relative to the respective resourcesfor the uplink communications. As shown, in association with the firstgrant, the UE accumulates TPC1 into the TPC state at T_(add1), and, inassociation with the second grant, accumulates TPC2 into the TPC stateat time T_(add2). Next, in association with determining a transmit powerfor UL2, the UE samples the TPC state at T_(sample2). As a result, asshown, a transmit power for UL2 will be based at least in part on TPC1and TPC2 (e.g., since TPC1 and TPC2 were accumulated into the TPC statebefore the sampling of the TPC state at T_(sample2)). Similarly, inassociation with determining a transmit power for UL1, the UE samplesthe TPC state at T_(sample1). As a result, as shown, a transmit powerfor UL1 will be based at least in part on TPC1 and TPC2 (e.g., sinceTPC1 and TPC2 were accumulated into the TPC state before the sampling ofthe TPC state at T_(sample1)).

With reference to example 370 in FIG. 3B, the UE may be configured todetermine T_(sample) relative to the respective grants and may beconfigured to determine T_(add) relative to the respective resources forthe uplink communications. As shown, in association with the firstgrant, the UE samples the TPC state at T_(sample2). As further shown, inassociation with the second grant, the UE samples the TPC state atT_(sample2). Next, the UE accumulates TPC2 into the TPC state atT_(add2). Then, the UE determines a transmit power for UL2 by addingTPC2 to a result of sampling the TPC state at time T_(sample2). Here,the UE may be configured to add TPC2 to the result of sampling the TPCstate at T_(sample2) since TPC2 was not accumulated into the TPC stateprior to or concurrently with sampling of the TPC state in associationwith determining a transmit power for UL2. Thus, as shown, the transmitpower for UL2 will be based at least in part on TPC2, but not TPC1(e.g., since TPC1 was not accumulated into the TPC state until afterT_(sample2)).

Similarly, the UE accumulates TPC1 into the TPC state at T_(add1). Then,the UE determines a transmit power for UL1 by adding TPC1 to a result ofsampling the TPC state at time T_(sample1). Here, the UE may beconfigured to add TPC1 to the result of sampling the TPC state atT_(sample1) since TPC1 was not accumulated into the TPC state prior toor concurrently with sampling of the TPC state in association withdetermining a transmit power for UL1. Thus, as shown, the transmit powerfor UL1 will be based at least in part on TPC1, but not TPC2 (e.g.,since TPC2 was not accumulated into the TPC state until afterT_(sample1)).

With reference to example 380 in FIG. 3B, the UE may be configured todetermine both T_(sample) and T_(add) relative to the respectiveresources associated with the respective uplink communications (ratherthan the respective grants). As further shown, the UE may be configuredsuch that an amount of time between the grant and T_(sample) matches anamount of time between the grant and T_(add). As shown, in associationwith the second grant, the UE accumulates TPC2 into the TPC state andsamples the TPC state at time T_(add) 2 (which matches timeT_(sample2)). As a result, as shown, a transmit power for UL2 is basedat least in part on TPC2 but not TPC1 (e.g., since TPC1 will not beaccumulated into the TPC state until after the sampling of the TPC stateat T_(sample2)). As further shown, in association with the first grant,the UE accumulates TPC1 into the TPC state and samples the TPC state attime T_(add) (which matches time T_(sample1)). As shown, a transmitpower for UL1 will be based at least in part on TPC1 and TPC2 (e.g.,since both TPC1 and TPC2 were accumulated into the TPC state before orconcurrently with the UE sampling the TPC state at T_(sample1)).

As indicated above, FIGS. 3A and 3B are provided as examples. Otherexamples may differ from what is described with respect to FIGS. 3A and3B. Notably, while the above described techniques are described in thecontext of transmit power control, these techniques may be applied inassociation with another state variable (e.g., other than the TPC state)that is needed to determine a parameter for a granted uplinkcommunication. For example, a beam indication, included in a grant, mayrefer to a reference signal, but a state and/or a beam associated withthe reference signal may itself be updated in an interval between thegrant and a granted resource, in a manner similar to that describedabove. In such a case, different definitions of beam-state can be usedby defining T_(sample) appropriately.

FIG. 4 is a diagram illustrating an example process 400 performed, forexample, by a UE, in accordance with various aspects of the presentdisclosure. Example process 400 is an example where a UE (e.g., UE 120)performs transmit power control with flexible scheduling delay.

As shown in FIG. 4, in some aspects, process 400 may include receiving atransmit power control (TPC) command in a grant associated withtransmitting an uplink communication, wherein a scheduling delay betweenthe grant and the uplink communication is a flexible scheduling delay(block 410). For example, the UE (e.g., using antenna 252, receiveprocessor 258, controller/processor 280, and/or the like) may receive aTPC command in a grant associated with transmitting an uplinkcommunication, wherein a scheduling delay between the grant and theuplink communication is a flexible scheduling delay, as described above.

As shown in FIG. 4, in some aspects, process 400 may include sampling aTPC state in association with determining a transmit power fortransmitting the uplink communication (block 420). For example, the UE(e.g., using controller/processor 280, transmit processor 264, and/orthe like) may sample a TPC state in association with determining atransmit power for transmitting the uplink communication, as describedabove.

As shown in FIG. 4, in some aspects, process 400 may include determiningthe transmit power based at least in part on the TPC state and the TPCcommand (block 430). For example, the UE (e.g., usingcontroller/processor 280, transmit processor 264, and/or the like) maydetermine the transmit power based at least in part on the TPC state andthe TPC command, as described above.

Process 400 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, timing associated with sampling the TPC state isrelative to the grant.

In a second aspect, alone or in combination with the first aspect,timing associated with sampling the TPC state is relative to a resourceassociated with transmitting the uplink communication.

In a third aspect, alone or in combination with any one or more of thefirst and second aspects, when timing of the TPC state being sampledcoincides with timing of at least one TPC command that is to beaccumulated into the TPC state, the TPC state is sampled after the atleast one TPC command is accumulated into the TPC state.

In a fourth aspect, alone or in combination with any one or more of thefirst through third aspects, when timing of the TPC state being sampledcoincides with timing of at least one TPC command that is to beaccumulated into the TPC state, the TPC state is sampled before the atleast one TPC command is accumulated into the TPC state.

In a fifth aspect, in combination with the fourth aspect, when the atleast one TPC command is the TPC command, the TPC command is added to aresult of sampling the TPC state.

In a sixth aspect, alone or in combination with any one or more of thefirst through fifth aspects, timing of the TPC state being sampled isbased at least in part on at least one of the scheduling delay betweenthe grant and the uplink communication, a grant type associated with thegrant, or a capability of the UE.

In a seventh aspect, alone or in combination with any one or more of thefirst through sixth aspects, timing of the TPC state being sampled issemistatically configured.

In an eighth sixth aspect, alone or in combination with any one or moreof the first through seventh aspects, timing of the TPC state beingsampled is dynamically determined.

In a ninth aspect, alone or in combination with any one or more of thefirst through eighth aspects, information associated with timing of theTPC state being sampled is at least one of: signaled in downlink controlinformation (DCI), a preconfigured constant, or a function of a DCIparameter.

In a tenth aspect, alone or in combination with any one or more of thefirst through ninth aspects, the uplink communication is one of: aphysical uplink shared channel (PUSCH) communication, a physical uplinkcontrol channel (PUCCH) communication, a sounding reference signal(SRS), or a physical random access channel (PRACH) sequence.

In an eleventh aspect, alone or in combination with any one or more ofthe first through tenth aspects, the TPC command is accumulated the TPCstate.

In a twelfth aspect, in combination with the eleventh aspect, timingassociated with accumulating the TPC command into the TPC state isrelative to the grant.

In a thirteenth aspect, in combination with any one or more of theeleventh and twelfth aspects, timing associated with accumulating theTPC command into the TPC state is relative to a resource associated withtransmitting the uplink communication.

In a fourteenth aspect, in combination with any one or more of theeleventh through thirteenth aspects, the TPC command is accumulated intothe TPC state before the TPC state is sampled.

In a fifteenth aspect, in combination with any one or more of theeleventh through fourteenth aspects, the TPC state is sampled before theTPC command is accumulated.

In a sixteenth thirteenth aspect, in combination with any one or more ofthe eleventh through fifteenth aspects, the TPC command is accumulatedinto the TPC state concurrently with the TPC state being sampled.

In a seventeenth aspect, in combination with any one or more of theeleventh through sixteenth aspects, timing of the TPC command beingaccumulated into the TPC state is based at least in part on at least oneof: the scheduling delay between the grant and the uplink communication,a grant type associated with the grant, or a capability of the UE.

In an eighteenth aspect, in combination with any one or more of theeleventh through seventeenth aspects, timing of the TPC command beingaccumulated into the TPC state is semistatically configured.

In a nineteenth aspect, in combination with any one or more of theeleventh through eighteenth aspects, timing of the TPC command beingaccumulated into the TPC state is dynamically determined.

In a twentieth aspect, in combination with any one or more of theeleventh through nineteenth aspects, information associated with timingof the TPC command being accumulated into the TPC state is at least oneof: signaled in downlink control information (DCI), a preconfiguredconstant, or a function of a DCI parameter.

Although FIG. 4 shows example blocks of process 400, in some aspects,process 400 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 4.Additionally, or alternatively, two or more of the blocks of process 400may be performed in parallel.

Although the discussions above have been with respect to determining thetransmit power for an uplink transmission, the same concepts also applywhen determining UL power headroom reports. These reports are computedbased on a maximum available transmit power per carrier (Pc,max) and theactual transmit power, or a virtual transmit power. A virtual transmitpower is a power computed when no actual UL transmission occurs, usingdefault assumptions for various parameters such as A-MPR, MCS, etc.which are normally associated with a UL transmission in the case thatsuch a transmission actually occurs. The computation of the actual orvirtual transmit power may be based on a TPC command and/or a TPC state,just as described above. For a given TPC process and closed-loop index,the TPC state used for this purpose may be the same as that used fordetermining the transmit power. Thus the Tadd value may be the same inboth cases. However, the T_(sample) time for transmit power computationmay or may not be same as that for power headroom report. Further, itmay be same or different for actual versus for virtual power headroomreports.

FIG. 5 is a diagram illustrating an example 500 of power headroomcalculation in a CA scenario with flexible scheduling, in accordancewith various aspects of the present disclosure. For the purposes of FIG.5, a UE (e.g., UE 120) is configured for carrier aggregation such thatthe UE can be scheduled for, and can transmit, uplink communications onmultiple component carriers (herein referred to as carriers).

As shown in FIG. 5, and by reference number 505, the UE may detect a PHRtrigger. The PHR trigger includes an event, detected by the UE, thatcauses the UE to calculate power headroom and provide, to a base station(e.g., BS 110), a PHR. In some aspects, in a CA scenario, the UE may beconfigured to provide a PHR that includes power headroom for all activecarriers (e.g., carriers on which transmission of an uplinkcommunication is scheduled). For example, the UE may provide a PHR thatincludes actual power headrooms for some carriers, and reference orvirtual power headrooms for other carriers. In some aspects, the UE maydetect the PHR trigger based at least in part on determining that anamount of path loss has changed by an amount that satisfies a threshold,based at least in part on expiration of a timer, and/or in anothermanner. In some aspects, the UE may be configured to transmit the PHR inan uplink communication associated with one of the multiple carriers. Insuch a case, the PHR, included in the uplink communication, may carrypower headrooms associated with one or more of the multiple carriers.

As shown by reference number 510, based at least in part on detectingthe PHR trigger, the UE may identify a set of carriers, of the multiplecarriers, that the UE should ignore when calculating a power headroom.In some aspects, the UE may ignore one or more carriers, of the multiplecarriers, in order to remove complexities introduced due to flexiblescheduling, as described below.

In some aspects, the UE may identify the set of carriers based at leastin part on determining that a set of uplink grants, each associated withone of the set of carriers, was received by the UE after a particulartime. For example, before detecting the PHR trigger, assume that the UEhas received, on a first carrier, a grant associated with scheduling anuplink communication on the first carrier. Next, the UE detects the PHRtrigger, after which the UE receives, on a second carrier, a grantassociated with scheduling an uplink communication on the secondcarrier. Notably, the grant on the second carrier is the earliest grantafter the PHR trigger. Additionally, after receiving the grant on thesecond carrier, the UE receives, on a third carrier, a grant associatedwith scheduling an uplink communication on the third carrier.

In this example, the UE may be configured to ignore carriers for whichuplink grants were received by the UE after a particular time, such as atime at which the earliest grant after the PHR trigger was received.Thus, in this case, the UE may identify the set of carriers to beignored as including the third carrier (e.g., since the grant wasreceived on the third carrier after the grant was received on the secondcarrier, which was the earliest grant after the PHR trigger). As aresult, in this example, the UE would calculate the power headroom forthe first carrier while taking into account transmit power associatedwith the second carrier, but without taking into account transmit poweron the third carrier. Similarly, the UE would calculate the powerheadroom for the second carrier while taking into account transmit powerassociated with the first carrier, but without taking into accounttransmit power on the third carrier.

Further, continuing with the above example, the UE may identify the setof carriers as including a fourth carrier on which no grant wasreceived. In other words, the UE may be configured to identify the setof carriers to be ignored based at least in part on determining that theUE has no uplink grants associated with the set of carriers, in someaspects.

In some aspects, the UE may identify the set of carriers to be ignoredas including all carriers, of the multiple carriers, other than thecarrier for which the UE is to calculate the power headroom. In thiscase, with reference to the above described scenario, the UE wouldcalculate the power headroom for the first carrier without taking intoaccount transmit power on the second carrier or the third carrier.Similarly, the UE would calculate the power headroom for the secondcarrier without taking into account transmit power on the first carrieror the third carrier.

In some aspects, the UE may identify the set of carriers to be ignoredbased at least in part on determining that a set of uplink grants, eachassociated with one of the set of carriers, was received by the UE aftera threshold amount of time from a time at which an uplink grant,associated with the carrier, was received by the UE. For example, for acarrier with a grant received in slot i, the UE may be configured toignore all other carriers whose grant comes at slot i+1 or later (e.g.,where slot i is the slot based on the SCS of the carrier).

As further shown in FIG. 5, and by reference number 515, the UE maycalculate the power headroom based at least in part on ignoring the setof carriers. For example, the UE may calculate the power headroom foreach active carrier, ignoring those carriers identified in the mannerdescribed above.

In some aspects, the UE may calculate the power headroom, associatedwith a given carrier, based at least in part on a particular uplinktransmission of at least two uplink transmissions associated withanother carrier. For example, an uplink transmission on a first carriermay at least partially overlap at least two uplink transmissions on asecond carrier (e.g., when the second carrier has a higher SCS than thefirst carrier). In this case, the UE may calculate the power headroom,associated with the first carrier, based at least in part on one of theat least two uplink transmissions associated with the other carrier. Insome aspects, the UE may be configured to calculate the power headroombased at least in part on an earliest uplink communication of the atleast two uplink communications. In some aspects, the UE may beconfigured to calculate the power headroom based at least in part on alast uplink communication of the at least two uplink communications. Insome aspects, the UE may be configured to calculate the power headroombased at least in part on an uplink transmission, of the at least twouplink transmissions, with a smallest or a largest power headroom,transmit power, assignment size, priority level (e.g., prioritize URLLCabove eMBB), and/or the like.

In some aspects, the UE may calculate the power headroom, associatedwith a given carrier, based at least in part on a particular uplinktransmission of at least two uplink transmissions associated with thegiven carrier. Continuing with the above example, the UE may calculatethe power headroom, associated with the second carrier, based at leastin part on the earliest uplink communication associated with the secondcarrier, the last uplink communication associated with the secondcarrier, or the uplink transmission, of the at least two uplinktransmissions, with the smallest power headroom.

As further shown in FIG. 5, by reference number 520, the UE may transmitthe PHR (e.g., to the BS) based at least in part on calculating thepower headrooms associated with the active carriers. In this way, a UEin a CA scenario may be configured to manage power headroom calculationfor uplink communications with flexible scheduling delay.

As indicated above, FIG. 5 is provided as an example. Other examples maydiffer from what is described with respect to FIG. 5.

FIG. 6 is a diagram illustrating an example process 600 performed, forexample, by a UE, in accordance with various aspects of the presentdisclosure. Example process 600 is an example where a UE (e.g., UE 120)performs power headroom calculation with flexible scheduling delay.

As shown in FIG. 6, in some aspects, process 600 may include detecting apower headroom report (PHR) trigger, wherein the UE is configured totransmit uplink communications using a plurality of carriers (block610). For example, the UE (e.g., using receive processor 258,controller/processor 280, transmit processor 266, and/or the like) maydetect a PHR trigger, wherein the UE is configured to transmit uplinkcommunications using a plurality of carriers, as described above.

As shown in FIG. 6, in some aspects, process 600 may includeidentifying, based at least in part on detecting the PHR trigger, a setof carriers, of the plurality of carriers, that is to be ignored whencalculating a power headroom associated with a carrier of the pluralityof carriers (block 620). For example, the UE (e.g., usingcontroller/processor 280, transmit processor 266, and/or the like) mayidentify based at least in part on detecting the PHR trigger, a set ofcarriers, of the plurality of carriers, that is to be ignored whencalculating a power headroom associated with a carrier, of the pluralityof carriers, as described above.

As shown in FIG. 6, in some aspects, process 600 may include calculatingthe power headroom based at least in part on an uplink transmission,associated with the carrier, and based at least in part on ignoring theset of carriers that is to be ignored (block 630). For example, the UE(e.g., using controller/processor 280, transmit processor 266, and/orthe like) may calculate the power headroom based at least in part on anuplink transmission, associated with the carrier, and based at least inpart on ignoring the set of carriers that is to be ignored, as describedabove.

Process 600 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, the set of carriers is identified based at least inpart on determining that a set of uplink grants was received by the UEafter a particular time, wherein each uplink grant, of the set of uplinkgrants, is associated with a respective carrier of the set of carriers.

In a second aspect in combination with the first aspect, the particulartime is a time at which a first grant was received after the PHR triggerwas detected.

In a third aspect, alone or in combination with any one or more of thefirst and second aspects, the set of carriers is identified based atleast in part on determining that the UE has no uplink grants associatedwith the set of carriers.

In a fourth aspect, alone or in combination with any one or more of thefirst through third aspects, the set of carriers includes all carriers,of the plurality of carriers, other than the carrier for which the powerheadroom is calculated.

In a fifth aspect, alone or in combination with any one or more of thefirst through fourth aspects, the set of carriers is identified based atleast in part on determining that a set of uplink grants was received bythe UE after a threshold amount of time from a time at which an uplinkgrant, associated with the carrier, was received by the UE, wherein eachuplink grant, of the set of uplink grants, is associated with arespective carrier of the set of carriers.

In a sixth aspect, alone or in combination with any one or more of thefirst through fifth aspects, the power headroom is calculated furtherbased at least in part on a particular uplink transmission of at leasttwo uplink transmissions associated with another carrier of theplurality of carriers, wherein the at least two uplink transmissions atleast partially overlap the uplink transmission associated with thecarrier.

In a seventh aspect, in combination with the sixth aspect, a subcarrierspacing, associated with the other carrier, is higher than a subcarrierspacing of the carrier.

In an eighth aspect, in combination with any one or more of the sixthand seventh aspects, the particular uplink transmission is a firstuplink transmission of the at least two uplink transmissions.

In a ninth aspect, in combination with any one or more of the sixththrough eighth aspects, the particular uplink transmission is a lastuplink transmission of the at least two uplink transmissions.

In a tenth aspect, in combination with any one or more of the sixththrough ninth aspects, the particular uplink transmission is an uplinktransmission, of the at least two uplink transmissions, with a smallestpower headroom.

In an eleventh aspect, alone or in combination with any one or more ofthe first through tenth aspects, the uplink transmission is a particularone of at least two uplink transmissions associated with the carrier.

Although FIG. 6 shows example blocks of process 600, in some aspects,process 600 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 6.Additionally, or alternatively, two or more of the blocks of process 600may be performed in parallel.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the aspects to the preciseform disclosed. Modifications and variations may be made in light of theabove disclosure or may be acquired from practice of the aspects.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software. Asused herein, a processor is implemented in hardware, firmware, or acombination of hardware and software.

As used herein, satisfying a threshold may, depending on the context,refer to a value being greater than the threshold, greater than or equalto the threshold, less than the threshold, less than or equal to thethreshold, equal to the threshold, not equal to the threshold, and/orthe like.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the aspects. Thus, the operation and behavior of thesystems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based, at leastin part, on the description herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various aspects. In fact, many ofthese features may be combined in ways not specifically recited in theclaims and/or disclosed in the specification. Although each dependentclaim listed below may directly depend on only one claim, the disclosureof various aspects includes each dependent claim in combination withevery other claim in the claim set. A phrase referring to “at least oneof” a list of items refers to any combination of those items, includingsingle members. As an example, “at least one of: a, b, or c” is intendedto cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combinationwith multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c,a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering ofa, b, and c).

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the terms “set” and “group” are intended to include oneor more items (e.g., related items, unrelated items, a combination ofrelated and unrelated items, etc.), and may be used interchangeably with“one or more.” Where only one item is intended, the phrase “only one” orsimilar language is used. Also, as used herein, the terms “has,” “have,”“having,” and/or the like are intended to be open-ended terms. Further,the phrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method of wireless communication performed by auser equipment (UE), comprising: receiving a transmit power control(TPC) command in a grant associated with transmitting an uplinkcommunication, wherein a scheduling delay between the grant and theuplink communication is a flexible scheduling delay; sampling a TPCstate in association with determining a transmit power for transmittingthe uplink communication; and determining the transmit power based atleast in part on the TPC state and the TPC command.
 2. The method ofclaim 1, wherein timing associated with sampling the TPC state isrelative to the grant.
 3. The method of claim 1, wherein timingassociated with sampling the TPC state is relative to a resourceassociated with transmitting the uplink communication.
 4. The method ofclaim 1, wherein, when timing of the TPC state being sampled coincideswith timing of at least one TPC command that is to be accumulated intothe TPC state, the TPC state is sampled after the at least one TPCcommand is accumulated into the TPC state.
 5. The method of claim 1,wherein, when timing of the TPC state being sampled coincides withtiming of at least one TPC command that is to be accumulated into theTPC state, the TPC state is sampled before the at least one TPC commandis accumulated into the TPC state.
 6. The method of claim 5, wherein,when the at least one TPC command is the TPC command, the TPC command isadded to a result of sampling the TPC state.
 7. The method of claim 1,wherein timing of the TPC state being sampled is based at least in parton at least one of: the scheduling delay between the grant and theuplink communication, a grant type associated with the grant, or acapability of the UE.
 8. The method of claim 1, wherein timing of theTPC state being sampled is semistatically configured.
 9. The method ofclaim 1, wherein timing of the TPC state being sampled is dynamicallydetermined.
 10. The method of claim 1, wherein information associatedwith timing of the TPC state being sampled is at least one of: signaledin downlink control information (DCI), a preconfigured constant, or afunction of a DCI parameter.
 11. The method of claim 1, wherein theuplink communication is one of: a physical uplink shared channel (PUSCH)communication, a physical uplink control channel (PUCCH) communication,a sounding reference signal (SRS), or a physical random access channel(PRACH) sequence.
 12. The method of claim 1, wherein the TPC command isaccumulated the TPC state.
 13. The method of claim 12, wherein timingassociated with accumulating the TPC command into the TPC state isrelative to the grant.
 14. The method of claim 12, wherein timingassociated with accumulating the TPC command into the TPC state isrelative to a resource associated with transmitting the uplinkcommunication.
 15. The method of claim 12, wherein the TPC command isaccumulated into the TPC state before the TPC state is sampled.
 16. Themethod of claim 12, wherein the TPC state is sampled before the TPCcommand is accumulated.
 17. The method of claim 12, wherein the TPCcommand is accumulated into the TPC state concurrently with the TPCstate being sampled.
 18. The method of claim 12, wherein timing of theTPC command being accumulated into the TPC state is based at least inpart on at least one of: the scheduling delay between the grant and theuplink communication, a grant type associated with the grant, or acapability of the UE.
 19. The method of claim 12, wherein timing of theTPC command being accumulated into the TPC state is semistaticallyconfigured.
 20. The method of claim 12, wherein timing of the TPCcommand being accumulated into the TPC state is dynamically determined.21. The method of claim 12, wherein information associated with timingof the TPC command being accumulated into the TPC state is at least oneof: signaled in downlink control information (DCI), a preconfiguredconstant, or a function of a DCI parameter.
 22. A user equipment (UE)for wireless communication, comprising: a memory; and one or moreprocessors operatively coupled to the memory, the memory and the one ormore processors configured to: receive a transmit power control (TPC)command in a grant associated with transmitting an uplink communication,wherein a scheduling delay between the grant and the uplinkcommunication is a flexible scheduling delay; sample a TPC state inassociation with determining a transmit power for transmitting theuplink communication; and determine the transmit power based at least inpart on the TPC state and the TPC command.
 23. The UE of claim 22,wherein timing associated with sampling the TPC state is relative to thegrant or is relative to a resource associated with transmitting theuplink communication.
 24. The UE of claim 22, wherein, when timing ofthe TPC state being sampled coincides with timing of at least one TPCcommand that is to be accumulated into the TPC state, the TPC state issampled after the at least one TPC command is accumulated into the TPCstate.
 25. The UE of claim 22, wherein, when timing of the TPC statebeing sampled coincides with timing of at least one TPC command that isto be accumulated into the TPC state, the TPC state is sampled beforethe at least one TPC command is accumulated into the TPC state.
 26. TheUE of claim 22, wherein timing of the TPC state being sampled is basedat least in part on at least one of: the scheduling delay between thegrant and the uplink communication, a grant type associated with thegrant, or a capability of the UE.
 27. The UE of claim 22, wherein theTPC command is accumulated the TPC state, wherein timing associated withaccumulating the TPC command into the TPC state is relative to the grantor is relative to a resource associated with transmitting the uplinkcommunication.
 28. The UE of claim 27, wherein timing of the TPC commandbeing accumulated into the TPC state is based at least in part on atleast one of: the scheduling delay between the grant and the uplinkcommunication, a grant type associated with the grant, or a capabilityof the UE.
 29. A non-transitory computer-readable medium storing one ormore instructions for wireless communication, the one or moreinstructions comprising: one or more instructions that, when executed byone or more processors of a user equipment (UE), cause the one or moreprocessors to: receive a transmit power control (TPC) command in a grantassociated with transmitting an uplink communication, wherein ascheduling delay between the grant and the uplink communication is aflexible scheduling delay; sample a TPC state in association withdetermining a transmit power for transmitting the uplink communication;and determine the transmit power based at least in part on the TPC stateand the TPC command.
 30. An apparatus for wireless communication,comprising: means for receiving a transmit power control (TPC) commandin a grant associated with transmitting an uplink communication, whereina scheduling delay between the grant and the uplink communication is aflexible scheduling delay; means for sampling a TPC state in associationwith determining a transmit power for transmitting the uplinkcommunication; and means for determining the transmit power based atleast in part on the TPC state and the TPC command.
 31. A method ofwireless communication performed by a user equipment (UE), comprising:detecting a power headroom report (PHR) trigger, wherein the UE isconfigured to transmit uplink communications using a plurality ofcarriers; identifying, based at least in part on detecting the PHRtrigger, a set of carriers, of the plurality of carriers, that is to beignored when calculating a power headroom associated with a carrier ofthe plurality of carriers; and calculating the power headroom based atleast in part on an uplink transmission, associated with the carrier,and based at least in part on ignoring the set of carriers that is to beignored.
 32. The method of claim 31, wherein the set of carriers isidentified based at least in part on determining that a set of uplinkgrants was received by the UE after a particular time, wherein eachuplink grant, of the set of uplink grants, is associated with arespective carrier of the set of carriers.
 33. The method of claim 32,wherein the particular time is a time at which a first grant wasreceived after the PHR trigger was detected.
 34. The method of claim 31,wherein the set of carriers is identified based at least in part ondetermining that the UE has no uplink grants associated with the set ofcarriers.
 35. The method of claim 31, wherein the set of carriers isidentified based at least in part on determining that a set of uplinkgrants was received by the UE after a threshold amount of time from atime at which an uplink grant, associated with the carrier, was receivedby the UE, wherein each uplink grant, of the set of uplink grants, isassociated with a respective carrier of the set of carriers.
 36. Themethod of claim 31, wherein the power headroom is calculated furtherbased at least in part on a particular uplink transmission of at leasttwo uplink transmissions associated with another carrier of theplurality of carriers, wherein the at least two uplink transmissions atleast partially overlap the uplink transmission associated with thecarrier.
 37. The method of claim 36, wherein a subcarrier spacing,associated with the other carrier, is higher than a subcarrier spacingof the carrier.
 38. The method of claim 36, wherein the particularuplink transmission is a first uplink transmission of the at least twouplink transmissions.
 39. The method of claim 36, wherein the particularuplink transmission is a last uplink transmission of the at least twouplink transmissions.
 40. The method of claim 36, wherein the particularuplink transmission is an uplink transmission, of the at least twouplink transmissions, with a smallest power headroom.
 41. The method ofclaim 36, wherein the uplink transmission is a particular one of atleast two uplink transmissions associated with the carrier.
 42. A userequipment (UE) for wireless communication, comprising: a memory; and oneor more processors operatively coupled to the memory, the memory and theone or more processors configured to: detect a power headroom report(PHR) trigger, wherein the UE is configured to transmit uplinkcommunications using a plurality of carriers; identify, based at leastin part on detecting the PHR trigger, a set of carriers, of theplurality of carriers, that is to be ignored when calculating a powerheadroom associated with a carrier of the plurality of carriers; andcalculate the power headroom based at least in part on an uplinktransmission, associated with the carrier, and based at least in part onignoring the set of carriers that is to be ignored.
 43. The UE of claim42, wherein the set of carriers is identified based at least in part ondetermining that a set of uplink grants was received by the UE after aparticular time, wherein each uplink grant, of the set of uplink grants,is associated with a respective carrier of the set of carriers.
 44. TheUE of claim 43, wherein the particular time is a time at which a firstgrant was received after the PHR trigger was detected.
 45. The UE ofclaim 42, wherein the set of carriers is identified based at least inpart on determining that the UE has no uplink grants associated with theset of carriers.
 46. The UE of claim 42, wherein the set of carriers isidentified based at least in part on determining that a set of uplinkgrants was received by the UE after a threshold amount of time from atime at which an uplink grant, associated with the carrier, was receivedby the UE, wherein each uplink grant, of the set of uplink grants, isassociated with a respective carrier of the set of carriers.
 47. The UEof claim 42, wherein the power headroom is calculated further based atleast in part on a particular uplink transmission of at least two uplinktransmissions associated with another carrier of the plurality ofcarriers, wherein the at least two uplink transmissions at leastpartially overlap the uplink transmission associated with the carrier.48. The UE of claim 47, wherein a subcarrier spacing, associated withthe other carrier, is higher than a subcarrier spacing of the carrier.49. The UE of claim 47, wherein the particular uplink transmission is afirst uplink transmission of the at least two uplink transmissions. 50.The UE of claim 47, wherein the particular uplink transmission is a lastuplink transmission of the at least two uplink transmissions.
 51. The UEof claim 47, wherein the particular uplink transmission is an uplinktransmission, of the at least two uplink transmissions, with a smallestpower headroom.
 52. The UE of claim 47, wherein the uplink transmissionis a particular one of at least two uplink transmissions associated withthe carrier.
 53. A non-transitory computer-readable medium storing oneor more instructions for wireless communication, the one or moreinstructions comprising: one or more instructions that, when executed byone or more processors of a user equipment, cause the one or moreprocessors to: detect a power headroom report (PHR) trigger, wherein theUE is configured to transmit uplink communications using a plurality ofcarriers; identify, based at least in part on detecting the PHR trigger,a set of carriers, of the plurality of carriers, that is to be ignoredwhen calculating a power headroom associated with a carrier of theplurality of carriers; and calculate the power headroom based at leastin part on an uplink transmission, associated with the carrier, andbased at least in part on ignoring the set of carriers that is to beignored.
 54. The non-transitory computer-readable medium of claim 53,wherein the set of carriers is identified based at least in part ondetermining that a set of uplink grants was received by the UE after aparticular time, wherein each uplink grant, of the set of uplink grants,is associated with a respective carrier of the set of carriers.
 55. Thenon-transitory computer-readable medium of claim 54, wherein theparticular time is a time at which a first grant was received after thePHR trigger was detected.
 56. The non-transitory computer-readablemedium of claim 53, wherein the set of carriers is identified based atleast in part on determining that the UE has no uplink grants associatedwith the set of carriers.
 57. The non-transitory computer-readablemedium of claim 53, wherein the set of carriers is identified based atleast in part on determining that a set of uplink grants was received bythe UE after a threshold amount of time from a time at which an uplinkgrant, associated with the carrier, was received by the UE, wherein eachuplink grant, of the set of uplink grants, is associated with arespective carrier of the set of carriers.
 58. The non-transitorycomputer-readable medium of claim 53, wherein the power headroom iscalculated further based at least in part on a particular uplinktransmission of at least two uplink transmissions associated withanother carrier of the plurality of carriers, wherein the at least twouplink transmissions at least partially overlap the uplink transmissionassociated with the carrier.
 59. The non-transitory computer-readablemedium of claim 58, wherein the uplink transmission is a particular oneof at least two uplink transmissions associated with the carrier.
 60. Anapparatus for wireless communication, comprising: means for detecting apower headroom report (PHR) trigger, wherein the apparatus is configuredto transmit uplink communications using a plurality of carriers; meansfor identifying, based at least in part on detecting the PHR trigger, aset of carriers, of the plurality of carriers, that is to be ignoredwhen calculating a power headroom associated with a carrier of theplurality of carriers; and means for calculating the power headroombased at least in part on an uplink transmission, associated with thecarrier, and based at least in part on ignoring the set of carriers thatis to be ignored.